If you run another SAS Solution for Solvency II cycle immediately after the conclusion of a previous cycle, SASServer8 might run out of memory. Toward the end of a cycle, certain colors are added to Microsoft Excel reports based on the EIOPA Validation Framework (Solvency II QRTs). This process uses jproxy processes that consume server RAM. When this step is over, the jproxies stay alive, consuming server RAM and preventing the server from recovering the RAM that has been used.

This can happen if the Java Virtual Machine (JVM) parameters on the workspace server are not set correctly. Here is the guidance from the deployment guide for SAS Solution for Solvency II:

Ensure that -JREOPTIONS is set to (-Xmx8192m -XX:+CMSClassUnloadingEnabled) in the sasv9.cfg file located in the directory \SAS-configuration-directory\Levn\SASApp\WorkspaceServer\

Here are more details about the -Xmx and -Xms settings:

• -Xmx specifies the maximum heap size. Set this parameter as large as you need it for your project (the recommendation is 8192m).
• -Xms specifies the minimum heap size. This should be left as the default value (128m). 

Note: The recommendations above are the opposite of the tuning advice for the middle tier, where you should keep these parameter values the same. On the middle tier, Java is used all the time, and you do not want the overhead of expanding and contracting the heap. On the workspace server, the JVM is used infrequently, so you want it to let go of the heap quickly.

Operating System and Release Information